Conversation
labkey-jeckels
left a comment
There was a problem hiding this comment.
- Should we add a link to this (and potentially other) reports. Maybe from the Admin Console?
- Should we add a minimal automated test that hits this action and checks for a few expected FKs?
My thought is no and no. Though I could be convinced otherwise. Traditionally, the DevTools module is for internal developers only. We haven't put these actions into the Admin Console or written tests for them, since the module is never installed on client servers. We can change that "rule," but, if so, we should probably add all these actions (and the TestController actions?) to the Admin Console and write tests for all of them. |
OK. Maybe a good future entry point to testing some of these will be to add coverage that ensures that we have the right FKs or indices in place |
Agreed |
Rationale
Developer action that could be helpful when investigating database performance problems. For now, simply reports all incoming foreign keys grouped by target table.